🎯 Goal

Fix an issue where CallParticipantState.custom field contains protobuf Value wrapper objects instead of native Dart types. This makes it difficult for developers to access custom participant data, as they need to manually unwrap each Value object to get the actual values.

The protobuf Struct type uses Value wrappers to represent dynamically-typed data, but when converting to the domain model, these should be unwrapped to native Dart types for easier consumption.

🛠 Implementation details

Changed the conversion in SfuParticipantExtension.toDomain() from:

custom: custom.fields,  // Returns PbMap<String, Value>

to:

custom: (custom.toProto3Json() as Map<String, Object?>?) ?? {},

🎨 UI Changes

N/A

🧪 Testing

This change can be tested by:

1. Joining a call with participants that have custom data fields
2. Accessing CallParticipantState.custom and verifying that values are native Dart types instead of protobuf Value objects
3. Verifying that nested structures (maps and lists) are properly unwrapped

Before the fix:

final participant = call.state.value.callParticipants.first;
final customField = participant.custom['custom_field'] as String; // throws "type 'Value' is not a subtype of type 'String' in type cast"

After the fix:

final participant = call.state.value.callParticipants.first;
final customField = participant.custom['custom_field'] as String; // success

☑️Contributor Checklist

General

• Assigned a person / code owner group (required)
• Thread with the PR link started in a respective Slack channel (#flutter-team) (required)
• PR is linked to the GitHub issue it resolves

☑️Reviewer Checklist

• Sample runs & works
• UI Changes correct (before & after images)
• Bugs validated (bugfixes)
• New feature tested and works
• All code we touched has new or updated Documentation

Summary by CodeRabbit

• Bug Fixes
  • Improved serialization of participant custom data to use a safe JSON fallback, preventing null or missing-field issues and ensuring consistent data handling across participants.